Because HyperDA does not support mathematical operations or date arithmetic, you should avoid designing handlers that depend on such calculations to determine where to go in response to a user’s navigation command. For example, if you were designing an appointment-tracking stack, you might have a button that moves the user forward in the stack by seven cards when he indicates he wants to advance one week from the currently visible card. Rather than using date arithmetic to calculate the date of the destination card (which would work fine in HyperCard), you might try seven go to next card statements. (Notice that it is not legal to use the repeat approach that might first come to mind because HyperDA does not support this command.)